Changes the static class design to function variable design.

Why?

To eliminate BC concerns by encapsulating the code for usage only during the plugin loading loops.

Once these loops are done, the variables are unset. This removes the code from global space, i.e.
meaning the code can't be accessed or used.

Removes changes outside of the wp-settings.php file.

Simplifies the code (less is better).

Collects the incompatible plugins from the loader loops.
After all plugins are loaded, then handles updating the options,
i.e. does it once instead of doing it for each plugin loader loop.

Introduces _get_plugin_wp_min_compatible_version().

By providing a global function, for-core plugins, such as Gutenberg,
can use it to check the minimum compatible version.

It provides a more foolproof way for the plugin to handle its response.

Doing a write to the database will have a performance hit.

To avoid the hit, removes the new "wp_force_deactivation_incompatible_plugins"
option in favor of hooking a callback into `'admin_notice'` and passing
the global into the callback via `use()`.

Isn't the global unset() within wp-settings.php?

Yes. It's done to avoid leaking the handler out of the file (for future BC).

Doesn't unsetting the global cause it to be unavailable to the hooked lambda?

No. Notice, the global is passed to the lambda (i.e. anonymous function)
via `use()`. What does this do? In PHP, the _value_ of the passed variable
gets inherited within the anonymous function is it (the anonymous function)
is defined, not when it (the anonymous function) is called.

See the PHP Manual
https://www.php.net/manual/en/functions.anonymous.php#functions.anonymous#example-541

>// Inherited variable's value is from when the function
>// is defined, not when called

See it in action https://3v4l.org/1BocJ.

Switches from not directly update the active plugins options
to using deactivate_plugins() via "admin_init".

Reverts the performance commit of using a lambda for the admin notice
as the notices need to persist to ensure they are rendered in
wp-admin. The option path persists between page loads, so that
when a user logs in or moves from frontend to backend, the notice
is shown.